Fix using the resolve-environment
Action with language aliases
#1923
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a bug that impacted the rollout of language aliases to default setup configurations that analyzed Go alongside at least one of the following languages:
The problem was that while we passed the CLI option to enable language aliasing to
resolve languages
, we also needed to pass it toresolve build-environment
.We have mitigated this by disabling language aliases in default setup until this fix is out.
Merge / deployment checklist